The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-22304	GEN000595	SV-52491r1_rule	DCNR-1 IAIA-1 IAIA-2	Medium

Description
Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes that are more vulnerable to compromise.

STIG	Date
HP-UX SMSE Security Technical Implementation Guide	2014-02-28

Details

Check Text ( C-47037r1_chk )
Note that in certain instances, the password field of any given password database may present as “” or “!!”, indicating that the account is locked or disabled. For Trusted Mode: Verify that the first 3 characters in the /tcb password hashes begin with the characters “$6$” (note that double quotes are for emphasis only). # cd /tcb/files/auth && cat /* \| egrep “:u_name=\|:u_pwd=“ If user account password hashes begins with any characters other than “$6$”, this is a finding. For SMSE: Verify that password hashes in /etc/shadow begin with the characters “$6$” (note that double quotes are for emphasis only). # cat /etc/shadow \| cut -f 2,2 -d “:” \| egrep -v “^\\*\|\\!\\!” If user account password hashes begins with any characters other than “$6$”, this is a finding.

Check Text ( C-47037r1_chk )

Note that in certain instances, the password field of any given password database may present as “*” or “!!”, indicating that the account is locked or disabled.

For Trusted Mode:
Verify that the first 3 characters in the /tcb password hashes begin with the characters “$6$” (note that double quotes are for emphasis only).
# cd /tcb/files/auth && cat */* | egrep “:u_name=|:u_pwd=“

If user account password hashes begins with any characters other than “$6$”, this is a finding.

For SMSE:
Verify that password hashes in /etc/shadow begin with the characters “$6$” (note that double quotes are for emphasis only).
# cat /etc/shadow | cut -f 2,2 -d “:” | egrep -v “^\\*|\\!\\!”

If user account password hashes begins with any characters other than “$6$”, this is a finding.

Fix Text (F-45450r1_fix)
For Trusted Mode: NOTE: There is no fix for Trusted Mode/Systems (TS). MD5 is currently used, and per vendor documentation, this algorithm will not be updated, due to TS being deprecated/replaced by SMSE. This will always result in a finding. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) to update the attribute. See the below example: CRYPT_ALGORITHMS_DEPRECATE=__unix__ CRYPT_DEFAULT=6 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

Fix Text (F-45450r1_fix)

For Trusted Mode:
NOTE: There is no fix for Trusted Mode/Systems (TS). MD5 is currently used, and per vendor documentation, this algorithm will not be updated, due to TS being deprecated/replaced by SMSE. This will always result in a finding.

For SMSE:
Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file.

Use the SAM/SMH interface (/etc/default/security file) to update the attribute. See the below example:
CRYPT_ALGORITHMS_DEPRECATE=__unix__
CRYPT_DEFAULT=6

Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database.

If manually editing the /etc/default/security file, save any change(s) before exiting the editor.